feat(interlink): private beta doc #3942
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RoRoJ
added
type: new content
bene2k1
reviewed
Nov 6, 2024
| Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. | ||
|
|
||
| <Message type="important"> | ||
| Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka allowed routes list) to the InterLink to allow traffic to flow. |
There was a problem hiding this comment.
Suggested change
| Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka allowed routes list) to the InterLink to allow traffic to flow. | |
| Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka [allowed routes list](/network/interlink/concepts/#allowed-routes-list) to the InterLink to allow traffic to flow. |
| @@ -0,0 +1,83 @@ | |||
| --- | |||
| meta: | |||
| title: InterLink - technical overview | |||
There was a problem hiding this comment.
Suggested change
| title: InterLink - technical overview | |
| title: InterLink - Technical overview |
| description: Dive deeper into understanding Scaleway's InterLink product, with technical diagrams, explanations and more. | ||
| noindex: true | ||
| content: | ||
| h1: InterLink - technical overview |
There was a problem hiding this comment.
Suggested change
| h1: InterLink - technical overview | |
| h1: InterLink - Technical overview |
|
|
||
| ### Hosted InterLinks | ||
|
|
||
| A hosted InterLink is provisioned via a [partner](/network/interlink/concepts/#partner). Partners are telcos or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/network/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. |
There was a problem hiding this comment.
Suggested change
| A hosted InterLink is provisioned via a [partner](/network/interlink/concepts/#partner). Partners are telcos or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/network/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. | |
| A hosted InterLink is provisioned via a [partner](/network/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/network/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. |
Comment on lines
+80
to
+83
|
|
||
|
|
||
|
|
||
|
|
There was a problem hiding this comment.
Remove additional empty lines at the end of file
|
|
||
| After placing the order via the API, the ID of the InterLink is returned in the response. You can use this ID to [check the status of your InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) at any time. | ||
|
|
||
| Immediately after ordering, it is expected that your InterLInk will briefly be in `Configuring` status, before moving to `Requested` status. |
There was a problem hiding this comment.
Suggested change
| Immediately after ordering, it is expected that your InterLInk will briefly be in `Configuring` status, before moving to `Requested` status. | |
| Immediately after ordering, it is expected that your InterLink will briefly be in `Configuring` status, before moving to `Requested` status. |
Comment on lines
+107
to
+109
|
|
||
|
|
||
|
|
| InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers. | ||
| </Message> | ||
|
|
||
| An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://scaleway-developers-production-internal.s3-website.fr-par.internal.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call. |
There was a problem hiding this comment.
Remove internal preview link
Suggested change
| An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://scaleway-developers-production-internal.s3-website.fr-par.internal.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call. | |
| An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call. |
| | **Active** | The InterLink is in a ready state, and traffic can flow. <br/><br/> The InterLink has been provisioned on both the Scaleway side and the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that allowed routes lists, route propagation, and an attached VPC are correctly configured). | | ||
| | **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited. <br/><br/> This may be the case if either, but not both of, the BGP IPv4 or IPv6 sessions are down. | | ||
| | **Down / All down** | The InterLink is provisioned, but there is no IP connectivity. <br/><br/> The InterLink has been provisioned successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. | | ||
| | **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket.| |
There was a problem hiding this comment.
Suggested change
| | **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket.| | |
| | **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Doc for InterLink private beta